To prepare for cross-team acceptance testing each team will need to do two steps.
Your instructor may follow a different approach on how the cross-team testing is executed. Make sure to get clarification on this PRIOR to the session where cross-team testing will take place
Ensure that your acceptance test plan spreadsheet IS UP-TO-DATE and identifies all of the user stories for Sprints 2 and 3 and includes the Acceptance Criteria for all of those stories. You should also indicate which stories you know are not yet implemented and should not be tested. You can identify the stories not to test by greying or in some way highlighting them.
Make sure that the spreadsheet has a file name starting with Acceptance Test Plan and that you DO NOT pre-fill the columns with results.
Exercises
Before-class Exercises
Acceptance testing plan - team (2 exercise points)
Per your instructor's guidance perform the steps specified above. If a zipfile is required, copy your implementation on a USB drive or in a place where it can be quickly accessed to ensure proper version is installed for testing on the appropriate machine(s).
Deposit your prepared "empty" Acceptance Test Plan spreadsheet file into Acceptance Test Plan - team Assignments folder in myCourses under Team Exercises area.
In-class Exercises
Cross-team acceptance testing: for these in-class exercises, the team will have two roles: as developers of a product being tested, and as testers of another team's product.
As the product developers (Unless instructed otherwise) complete the following:
Ensure the proper version of your software as well as a copy of the Acceptance Test Plan are available or installed on all machines that will be used by your testers.
Take notes as your testers voice their findings or concerns.
Answer any questions that the testers have while they are performing the tests but try not to "hand-hold" them or bias their interactions with your software.
As the product testers (Unless instructed otherwise) complete the following:
Validate that you can access the application to be tested and proper version of the Acceptance Test Plan.
Perform the acceptance testing by executing tests to determine if the product meets each acceptance criterion in the Acceptance Test Plan that has been identified as implemented. For each test, record the results of the test.
Especially for tests that fail, be specific in the comments that you provide to give the product developers as much information as possible describing the nature of the failure.
Add to the bottom of the Acceptance Test plan a separator and below it add "new" tests that may have been missing and/or comments which can benefit the team software you just tested.
Aggregate all test results and comments into one Acceptance Test Plan spreadsheet and make sure to give that back to the product developer(s).
Acceptance test results - team (2 exercise points)
When you have completed your testing as the product testers, rename the file to conform with Acceptance Test plan-ssteamX-testing-BY-ssteamY.xls for example Acceptance Test plan-09a-testing-BY-09b.xls (deposit the Acceptance Test Plan spreadsheet with the results of all of the tests that you performed into the Assigments folder in myCourses, Acceptance test results - team in the Team Exercises. Note: this is the file of results for the testing that your team performed on another team's product and you which you should have also given to the product developers for them to use your feedback.
